[PATCH 3/4] dnp3: set a bound on the number of points per message
authorJason Ish <jason.ish@oisf.net>
Wed, 7 Jan 2026 15:23:09 +0000 (09:23 -0600)
committerAndreas Dolp <dev@andreas-dolp.de>
Thu, 23 Apr 2026 05:14:21 +0000 (07:14 +0200)
commit406b198be65f7129e90aa14bc0459368ea009ff7
tree49cdbdb15a2f3b74a61da98f6a2d4f33fa879073
parent889f97c73bb9691a2b28e8d4d380bf3e4798ba48
[PATCH 3/4] dnp3: set a bound on the number of points per message

16384 is used as the max, but a configuration parameter has been
provided. The reason for setting an upper bound is that bit flags can
create a memory amplification as we parse them into individual data
structures.

Ticket: #8181
(cherry picked from commit 3a32bb5743c35afb3278a6448f7e9669512dbe92)

Origin: upstream, https://github.com/OISF/suricata/commit/fdd79bdb14488244604729f1d68ca4bc60000dbd.patch
Bug: https://redmine.openinfosecfoundation.org/issues/8181
Subject: Upstream fix for CVE-2026-22259 part 3

Gbp-Pq: Name CVE-2026-22259_3.patch
doc/userguide/upgrade.rst
rules/dnp3-events.rules
src/app-layer-dnp3.c
src/app-layer-dnp3.h
suricata.yaml.in